The following checks must be done
after any major interruption in Trading, and before any resumption in Trading
can be considered:
☐
Confirm all monitoring is working as expected:
☐
CH2 PROD-VDI is receiving stats and EMT updates from both CH2 and NY4
processes.
☐
NY4 PROD-VDI is receiving stats and EMT updates from both CH2 and NY4
processes.
☐ Solarwinds, Oracle Grid and Perfmons
are updating as expected (available from CH2 PROD-VDI only).
☐
Confirm CMA testing is working without issue, confirming all OSF-to-ME-to-QRS
functionality.
☐ CMACH2 testing all MEB instances via
DPB_CMACH2 process.
☐ CMANY4 testing all MEL and MEO instances
via DPB_CMANY4 process.
☐ CMAOMS testing all ME instances via
FSD_CMAOMS process.
☐ Confirm all Outbound
Market Data is connected and processing as expected.
☐
Use all four Bookfeed test issues to confirm all
outbound market data.
☐
Confirm QRS stats are updated as orders and trades are entered.
☐
Confirm TRS stats are updated as trades are entered.
☐
Confirm BFS stats are updated as orders and trades are entered.
☐
Use Clearing test issue to confirm clearing records are rejected by DTCC as
expected.
☐
Confirm all database loading is up to date for application startups.
☐ All CH2 and NY4 databases are up to date
from all processes running in both CH2 and NY4 data centers.
☐
Confirm all quotes and trades from SIP are being received and processed by MEs.
☐ CH2 SIP-to-CHX stats monitors are updating
from both SIAC and NASD, Primary and Alt channels.
☐ NY4 SIP-to-CHX stats monitors are updating
from both SIAC and NASD, Primary and Alt channels.
☐
Confirm CH2 Brokerplex Market Data queries return
data for at least one test connectivity issue from each ME.
☐
Confirm NY4 Brokerplex Market Data queries return
data for at least one test connectivity issue from each ME.
☐
Confirm all Brokerplex to ME connectivity is working
as expected, confirming BPLX to ME connectivity.
☐
From CH2 Brokerplex, send at least 1 Brokerplex cross to every ME using test connectivity
issues.
☐
From NY4 Brokerplex, send at least 1 Brokerplex cross to every ME using test connectivity
issues.
☐ Confirm all cross-datacenter test firm
connections are established and have simulators connected.
☐ From NY4 PROD-VDI OSF Simulator, send
order to DPB_DAST (running in CH2).
☐ From NY4 PROD-VDI OSF Simulator, send
order to FSD_FIXTB (running in NY4).
☐ From CH2 PROD-VDI OSF Simulator, send
order to DPB_DAST2 (running in NY4).
☐ From CH2 PROD-VDI OSF Simulator, send
order to FSD_FIXT (running in CH2).
☐ Confirm CSI, Maintenance Client and MROL
queries working as expected.
☐ CSI queries of orders and trades occurring
after each application’s time of recovery being the most imperative.
(continued
on next page)
☐ If Binary Database Loader for OPCON is up
to date, check for the following in the ER:
☐ abort
☐ alert
☐ data is
☐ disconnect
☐
dupe
☐ error
☐ fail
☐ (space) gap
☐ invalid
☐ loss
☐ lost
☐ market data download complete
☐ ora-
☐ processed in
☐ rej
☐ trib
☐ unable
☐ warn